Get the eventSourceArn from $snsRecord->getTopicArn instead of getEve… #87
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
While trying to consume SNS events, I encountered the error
No transport found for eventSource
in\Bref\Symfony\Messenger\Service\MessengerTransportConfiguration
. Upon investigation, I discovered that the$eventSourceArn
passed to theprovideTransportFromEventSource
method includes aMessageId
, resulting in an ARN likesns://arn:aws:sns:eu-central-1:account-id:sns-topic-name:9d572d5f-a88c-49df-9f61-81270fdb55fc
.Since each event has a different MessageId, this always triggers the
No transport found for eventSource
error.This PR addresses the issue by using
$snsRecord->getTopicArn()
instead of$snsRecord->getEventSubscriptionArn()
.@mnapoli. I would greatly appreciate it if you could review this PR, as this issue is a blocker for consuming SNS events in our project.